Continues the Server Features work with activation persistence and UX polish.

- Persistence (mock): new internal table 8360 "MCP Feature Activation" holds the
  API Tools / AL Query Tools activation flags keyed by config SystemId, behind four
  MCP Config Implementation procedures (EnableAPITools/EnableALQueryTools and
  IsAPIToolsEnabled/IsALQueryToolsEnabled). These flags belong on the platform-owned
  MCP Configuration table, which the app can't extend; every mock site is tagged
  "// MOCK:" and Appendix E of the design doc lists the exact steps to remove them.
- Gate: EnableDynamicToolMode now requires API Tools to be enabled first
  (APIToolsRequiredForDynamicErr) - previously a platform-pending stub.
- Dynamic Tool Mode renders as an indented sub-feature of API Tools
  (interface TryGetParentFeature + MCP Server Feature.Indentation).
- UI polish: align the curated list with "Available APIs" terminology (action and
  field renames), drop the Server Feature column from the System Tools factbox, and
  promote Export/Import on the config list.
- Tests: enable API Tools before Dynamic Tool Mode so the new gate is satisfied.
- Docs: design doc D30-D32, Appendix C #20-22, Appendix D #12-13, and a new
  Appendix E "Productionizing - removing the mocks". D32 / Appendix D #13 record the
  card list-part "always collapsed" investigation (BC platform limitation, AL #6258).

AB#631012

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>